Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.99%. Comparing base (ae766ca) to head (c126751).
⚠️ Report is 1 commits behind head on main.

@@           Coverage Diff           @@
##             main    #1330   +/-   ##
=======================================
  Coverage   94.99%   94.99%           
=======================================
  Files          42       42           
  Lines        2755     2759    +4     
=======================================
+ Hits         2617     2621    +4     
  Misses        138      138           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Would it be more appropriate to have the docs url be at /, or to have / redirect to /docs?

My concerns are that:

1. We may use / in the future (and still want to docs)
2. I don't know how standardised /docs is, and whether the change would cause more confusion that it's worth

I think having / as the docs page is the better option then redirecting /docs to /.
These are my thoughts on your questions

1. I don't think we are planning to host any UI at ixx-blueapi.diamond.ac.uk So using root should be okay.
   But even if we have to host a UI then that UI can have a link to the docs page which can be hosted at any location
2. I think having the docs page at the root is the most natural place for the documentation to live because anyone that goes to "ixx-blueapi.diamond.ac.uk" goes only to find the docs page for blueapi.
   To mitigate this we should inform people on athena channel that this is where the docs page is going to live from now on.
   (I think this will definitely have a positive reaction as you can see for the reaction on module load going to the correct namespace that you need)

Okay let's go for it.

Should we also have a redirect from the now empty /docs to the new /, or is that overkill?

Okay let's go for it.

Should we also have a redirect from the now empty /docs to the new /, or id that overkill?

I think that is overkill

We should also get some opinions from @DiamondLightSource/developers-daq-core

Having / not be a 404 would be great improvement - going through the auth login for p4x and ending up with a not-found is surprising.

Personally I think making / redirect to /docs for now would be the better option so that if we have something else in future at the root it wouldn't render anything that refers to / out of date.

Alternatively it could be a landing page with readme level docs/status on - stuff like current version and where to find other services (tiled/glazed/numtracker) as well as a link to the current jsonapi docs and the general docs.

Not completely against moving the api docs to /, but they should probably still be available at /docs through a redirect (at least for a while) as people are expecting them to be there.

You can have a look at this PR to check how you can do redirect